home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: presby.edu!jtbell
- From: jtbell@presby.edu (Jon Bell)
- Subject: Re: Coding Standards
- Message-ID: <DnvvFC.Hvq@presby.edu>
- Date: Thu, 7 Mar 1996 06:01:59 GMT
- References: <4hj8ek$elu@sam.inforamp.net> <4hjh5c$elk@flood.weeg.uiowa.edu> <4hlreg$6jg@sam.inforamp.net>
- Organization: Presbyterian College, Clinton, South Carolina USA
-
- Randy Charles Morin <rmorin@inforamp.net> wrote:
- >In article <4hjh5c$elk@flood.weeg.uiowa.edu>,
- > maclenna@ozone.uiowa.edu (Mark MacLennan) wrote:
- >>> -optimize code only when you have a problem. So we can't optimize
- >>>size in order to anticipate that code size will be a problem. First we have
- >>>to experience the problem (most likely in the field).
- >>Perhaps they want well-written code that they and other
- >>future programmers can read rather than tricky "optimized" code.
- >>The code can always be tweaked for specific hardware at a later
- >>time. There is no reason that you can't write efficient code using
- >>appropriate algorithms and data structures.
- >
- >Read the above. It says no optimizations until you have a problem. Yet you
- >are still optimizing before any problems.
-
- How about testing and profiling the code to find the problem spots, and
- pointing them out to the customer *before* you hand over the finished
- product?
-
- --
- Jon Bell <jtbell@presby.edu> Presbyterian College
- Dept. of Physics and Computer Science Clinton, South Carolina USA
-